The Publisher Automation Security Level must be configured for high security.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-26708	DTOO323 - Publisher	SV-34093r1_rule	ECSC-1	Medium

Description
When a separate application is used to launch Publisher 2010 programmatically, any macros can run in the programmatically-opened application without being blocked. Disabling or not configuring this setting could allow a malicious user to use automation to run malicious code in Publisher 2010.

STIG	Date
Microsoft Publisher 2010	2014-01-07

Details

Check Text ( C-34495r1_chk )
The policy value for User Configuration -> Administrative Templates -> Microsoft Publisher 2010 -> Security “Publisher Automation Security Level” must be set to “Enabled and High (Disabled)" is selected. Procedure: Use the Windows Registry Editor to navigate to the following key: HKCU\Software\Policies\Microsoft\Office\Common\Security Criteria: If the value AutomationSecurityPublisher is REG_DWORD = 3, this is not a finding.

Check Text ( C-34495r1_chk )

The policy value for User Configuration -> Administrative Templates -> Microsoft Publisher 2010 -> Security “Publisher Automation Security Level” must be set to “Enabled and High (Disabled)" is selected.

Procedure: Use the Windows Registry Editor to navigate to the following key:

HKCU\Software\Policies\Microsoft\Office\Common\Security

Criteria: If the value AutomationSecurityPublisher is REG_DWORD = 3, this is not a finding.

Fix Text (F-30020r1_fix)
Set the policy value for User Configuration -> Administrative Templates -> Microsoft Publisher 2010 -> Security “Publisher Automation Security Level” to “Enabled and High (Disabled)" is selected.